Supabase setup

Create and configure a Supabase project for TuPerfil.net, including running the initial migration and creating the first admin user.

TuPerfil.net uses Supabase for the PostgreSQL database, authentication, and file storage. Follow these steps to create a new project and prepare it for the application.

1. Create a Supabase account

   Go to supabase.com and sign up or log in. The free tier is sufficient for development and small production deployments.

2. Create a new project

   From the Supabase dashboard, click New project and fill in:

   • Name — e.g. tuperfil-net
   • Database password — choose a strong password and save it somewhere safe; you will not need it day-to-day, but you may need it to connect via direct Postgres tooling
   • Region — choose the region closest to your users (e.g. South America for an Argentine audience)

   Click Create new project and wait about one minute for provisioning to complete.

3. Run the initial schema migration

   Open SQL Editor in the left sidebar, click New query, paste the full contents of supabase/migrations/001_initial_schema.sql, and click Run.

   This migration creates the core schema:

   • categories table with the six default news categories
   • articles table with RLS policies (public read for published articles, authenticated write)
   • contacts table (public insert, authenticated read)
   • article-images storage bucket with public read and authenticated write policies
   • update_updated_at() trigger function

   After running migration 001, continue running migrations 002 through 019 in order. See the Migrations page for the full list and instructions.

4. Get your API keys

   Go to Settings → API in the Supabase dashboard. You need three values:

   Key	Field in dashboard	Variable name
   Project URL	Project URL	NEXT_PUBLIC_SUPABASE_URL
   Anon key	Project API keys → anon public	NEXT_PUBLIC_SUPABASE_ANON_KEY
   Service role key	Project API keys → service_role secret	SUPABASE_SERVICE_ROLE_KEY

   Copy these into your .env.local file. See Environment variables for details.

5. Create the first admin user

   Go to Authentication → Users → Add user → Create new user. Enter an email address and a secure password.

   This is the account you will use to log in at /admin.

   If you have already run migration 012_user_roles.sql, the first user created automatically receives the admin role. Subsequent users receive the editor role. You can change roles directly in the profiles table via the Table Editor.

6. (Optional) Run seed data

   If you want sample articles to test the public site, open the SQL Editor, paste the contents of supabase/seed.sql, and run it.

   The seed script automatically uses the first user in auth.users as the author, so it works without any manual substitution. It creates one published article in each of the six categories:

   Category	Article
   Perfil Político	Government economic measures
   Perfil Judicial	Historic corruption ruling
   Perfil Salud	Record vaccination campaign
   Perfil Deportivo	Local team reaches national final
   Perfil Regional	New water treatment plant
   Perfil Internacional	Climate summit historic agreements

   Seed data is useful for verifying that the homepage, category pages, and article pages all render correctly before publishing real content.

Row Level Security

RLS is enabled on every table in the schema. You do not need to configure it manually — the migrations set up the correct policies. The key rules are:

Table	Anonymous (unauthenticated)	Authenticated
articles	Read published, non-deleted articles	Full CRUD
categories	Read all	Full CRUD
contacts	Insert only	Read, update, delete
comments	Insert; read approved only	Full CRUD
subscribers	Insert (subscribe)	Read, update, delete
ads	Read active ads	Full CRUD
breaking_news	Read all	Insert, update
page_views	Insert	Read
ad_events	Insert	Read

Do not disable RLS on any table. The application relies on these policies to keep unpublished articles and contact messages private.

Allowed URL origins

After you deploy to Vercel (or any custom domain), add your production URL to Authentication → URL Configuration → Site URL and Redirect URLs. Without this, Supabase will reject authentication callbacks from your production domain.